Version control methodology for network model

ABSTRACT

Disclosed are methods and apparatus for providing version control for a model. A database ( 102 ) is divided into three logical areas corresponding to working model area ( 120 ), full model area ( 122 ), and permanent model area ( 124 ). Data, which may be CIM formatted data, imported into the model is validated against data previously stored in the full model area ( 122 ) and version controlled based in part on timestamp data. The version controlled data may then be exported for use by network applications. Imported data may come from a power system utility while the exported data may be used for control of such a utility.

FIELD OF THE INVENTION

The present subject matter is directed to methodologies for providingversion control for a network model for an electric utility.

BACKGROUND OF THE INVENTION

In an electric utility, there are usually several systems that maintainand/or utilize data representing the structure of the electricalnetwork. These systems may include, without limitation, GeographicInformation Systems (GIS), Design Systems, CAD Systems, Asset ManagementSystems, SCADA Systems, Outage Management Systems (OMS), DistributionManagement Systems (DMS), and Energy Management Systems (EMS)

Some of these components may be “homegrown” within a utility, whileothers are likely to be commercially available products, orsite-specific implementations based on such products. Model managementis a term that may be used to refer to the processes associated withmaintaining consistency between network representations stored by thesevarious systems and the real-world network.

Clearly, model management is about integration and synchronization.Previous efforts have been made to integrate existing OMS and DMSproduct offerings. One area in which it is expected that previousexperiences can be leveraged to improve energy management and controlsystems, such as an OMS/DMS, is that of GIS Data Integration. Forexample, it would be desirable to develop the ability to accept networkdata from an external GIS to populate the operational OMS/DMS thusreducing the time and effort to set up and deploy an OMS/DMS.

It is recognized that in many deployments, such integration wouldrequire the transformation of network information from a geographic to aschematic form. In this case, the chosen path for integration betweensystems was the IEC TC57 WG13 and WG14 61968 61970 model. This is simplyreferred to as the CIM model and is a standard for exchanging theelectrical network between systems. The data is both initial load andincremental updates to the network as distribution networks changefrequently.

It would be advantageous, therefore, to provide a methodology ofmanaging a large-scale normal state network model from the electricpower transmission and distribution domain. It would be furtheradvantageous to provide a methodology wherein frequently changed normalstate network data can be stored and version controlled so that the datamay be conveniently used by other applications.

BRIEF DESCRIPTION OF THE INVENTION

Aspects and advantages of the invention will be set forth in part in thefollowing description, or may be obvious from the description, or may belearned through practice of the invention.

The present subject matter relates to a method for providing versioncontrol for an electrical network model. The method provides a databasethat is divided into plural logical areas including at least a workingmodel logical area and a permanent model logical area. Data is importedinto the working model logical area and version information that isbased at least in part on a timestamp is associated with the importeddata. The imported data and associated version information is thenstored in the permanent model logical area.

In other embodiments, the method provides a full model logical area inthe database and provides for importing full model data into the fullmodel logical area. In such embodiments, imported incremental changedata is validated at least in part on the full model data and mergedwith data stored in the working model logical area. These methods alsoprovide for storing the merged data in the full model logical area.

The present subject matter also relates to methods for controllingoperation of a network. These methods provide a database that is dividedinto plural logical areas including at least a working model logicalarea and a permanent model logical area. These methods provided forimporting data into the working model logical area, associating versioninformation that is based at least in part on a timestamp with theimported data, storing the imported data and associated versioninformation as version controlled data in the permanent model logicalarea, and exporting the version control data for use by networkapplications. Again the standard CIM is used for communicating the modelto other systems. In selected further embodiments, these methods furtherprovide a full model logical area in the database in which full modeldata is imported. These selected embodiments provide for validatingimported incremental change data based at least in part on the fullmodel data, merging validated incremental change data with data storedin the working model logical area, and storing the merged data in thefull model logical area. In selected methods, validation is based atleast in part on a profile of a standard model and may also be based atleast in part on phase and connectivity information.

The present subject matter also relates to an apparatus for controllingoperation of a network. Such apparatus may correspond to a databasedivided into plural logical areas including at least a working modellogical area and a permanent model logical area. The apparatus may alsoinclude a data import manager for receiving data into the working modellogical area, a version control configured to associate versioninformation based at least in part on a timestamp with the data receivedby the data import manager, an archive manager configured to store theimported data and associated version information as version controlleddata in the permanent model logical area of the database, and an exportmanager configured to export the version control data for use by networkapplications.

In selected particular embodiments, the apparatus may also include afull model logical area in the database, a validation manager configuredto validate imported incremental change data received by the importmanager based at least in part on data stored in said full model logicalarea, a baseline manager configured to merge validated incrementalchange data with data stored in the working model logical area, and adatabase manager configured to store the merged data in the full modellogical area.

These and other features, aspects and advantages of the presentinvention will become better understood with reference to the followingdescription and appended claims. The accompanying drawings, which areincorporated in and constitute a part of this specification, illustrateembodiments of the invention and, together with the description, serveto explain the principles of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

A full and enabling disclosure of the present invention, including thebest mode thereof, directed to one of ordinary skill in the art, is setforth in the specification, which makes reference to the appendedfigures, in which:

FIG. 1 provides an overview of a model exchange platform incorporatingversion control in accordance with present technology; and

FIG. 2 illustrates an exemplary conceptual architecture for modelmanagement.

Repeated use of reference characters throughout the presentspecification and appended drawings is intended to represent the same oranalogous features or elements of the invention.

DETAILED DESCRIPTION OF THE INVENTION

Reference now will be made in detail to embodiments of the invention,one or more examples of which are illustrated in the drawings. Eachexample is provided by way of explanation of the invention, notlimitation of the invention. In fact, it will be apparent to thoseskilled in the art that various modifications and variations can be madein the present invention without departing from the scope or spirit ofthe invention. For instance, features illustrated or described as partof one embodiment can be used with another embodiment to yield a stillfurther embodiment. Thus, it is intended that the present inventioncovers such modifications and variations as come within the scope of theappended claims and their equivalents.

In accordance with present technology, a modeling solution has beenprovided that allows electrical network data to be entered once and usedin multiple places while making it possible to integrate multiple andvarying systems including GIS and operational systems. Further, thepresent technology provides control over the processes associated withmaking network data available for use in different places.

With reference to FIG. 1, a model exchange platform (MEP) 100,constructed in accordance with present technology, is designed to managenormal state network models that can be applied, for example, in theoperation of electrical utilities. Those of ordinary skill in the artwill appreciate, however, that the present subject matter may beemployed with other types of network models as well.

When a normal state network model is imported from other applications bythe MEP 100, the MEP is able to validate the data, store the data, andversion control the validated data automatically. Once the data isversion-controlled, the data can be exported, to be used by otherapplications or systems within the utility.

As represented in FIG. 1, all normal state network CIM 110 that isimported into the MEP 100 is stored into a database 102 so that thesystem may version control 112 the data within the database. Database102 is divided into three logical model areas corresponding to WorkingModel area 120, Full Model area 122, and Permanent Model area 124. Eachmodel area 120, 122, 124 has its own functional purpose as outlinedbelow.

Working Model area 120 is used to temporarily store the original CIMdata 110 imported from, for example, a power system utility (notseparately illustrated). This imported CIM data 110 may correspond toincremental change data. Such incremental changes of the normal state ofthe network are parsed and mapped into records in the database.

Full Model area 122 stores the validated and merged models from theWorking Model area 120. Validation is based on the latest full model. Inan exemplary embodiment, the model data may be imported formatted in thedata standard of the IEC TC57 Working Groups 13 and 14. Those ofordinary skill in the art will appreciate that this standard correspondsto International Electrotechnical Commission Technical committee 57standards relating to energy management (Working Group 13) anddistribution management (Working Group 14). Validation occurs based onprofiles of the 61968 and 61970 standard models developed for theseWorking Groups as are known by those of ordinary skill in the art. Inaccordance with present technology, the model may also be validated forphases and connectivity.

Permanent Model area 124 stores all the validated incremental changesfrom Working Model area 120, which will be labeled with a version andstored permanently.

MEP 100 version control models in the Permanent Model area 124 based ona timestamp. In an exemplary configuration of the present subjectmatter, an automatically created version may include the followinginformation: version ID, version name, model type, model source, modelsummary information, version operator, version created timestamp,comments, and other related information. The version ID may beincremented based on the import timestamp.

There are several components to the network data that are utilized inoperational systems that may be generally referred to as Back-OfficeSystems that generally are concerned with various information types.These include, without limitation, Asset Information, ConnectivityInformation, Special Information, and Customer Information.

Asset Information includes both objects and data. Objects include,without limitation, Supply Points, i.e., Power Sources, Devices,Conductors, and Demand Points including both metered and unmeteredpoints. Data includes, without limitation, Identifiers, ElectricalAttributes, Control Information, and Measurement Information. In certaininstances, an asset can be defined across multiple systems. In theseinstances, the model manager may be configured to act as a “phone book”for managing what system has what information. In this way, the modelmanager may be configured to support queries and thereby provide furthersystem information.

Connectivity Information describes how assets are connected to oneanother to support the flow of power. Spatial Information providesinformation regarding asset location while Customer Information providesinformation regarding Customers that are connected to the network.

The systems that provide these data, either initially or on an ongoingbasis, are diverse or include, without limitation: Asset ManagementSystems, SCADA Systems that provide identifiers and control andmeasurement definitions, GIS, CIS, CAD systems, and Legacy Databases.

In some ways, all of these systems can be generalized into possibleproviders of network definition data. It is possible that components ofoperational systems will even play this role, if, for example, networkdata maintenance is carried out using capabilities that those systemsprovide.

In most of the world, electrical utilities record their assets and theirgeographic layout in a GIS. This is especially true for OMS systems andincreasingly for DMS systems. Any of a number of GIS systems is likelyto be in place at a utility, including, for example, those developed byGE Smallworld, Intergraph and ESRI.

With reference to FIG. 2, generally it is expected that the dataprovided by a GIS 204 will include some, but not all, asset informationconnectivity information and spatial information. Information comingfrom a GIS may or may not include identifiers that can be understood byall systems. Data from other systems may need to be matched up with GISdata before it can be used in operational systems.

As well as providing network information in an initial “bulk load”fashion, the GIS may be employed to provide incremental updates. Thetiming and packaging of such incremental updates is likely to be quitevariable. Updates may be available in a “proposed” form before they arecarried out in the field, or they may be available only as “as-built”updates. They may be packaged in chunks that correspond closely to anoriginating design/construction effort or they may be quiteunstructured.

Besides acting as sources of data, it is likely that a GIS 204 will alsoreceive network data. This data may be of quite low volume, such aspermanent changes being fed back to the GIS from operational systems.Alternatively, there is the potential for higher volumes of data to bereceived by the GIS if it isn't the place where updates are originated.

In some utilities, CAD 206 systems are the primary repository ofgraphical, i.e., geographic or schematic, data. This data may be inaddition to data stored in a GIS, and may only be maintained for certainparts of the network. Essentially, the information content of suchrepositories is likely to be similar to that stored in a GIS and mayinclude some, but not all, asset information, connectivity information,graphical information, and the DBMS 208.

Other systems of one sort or another are likely to provide informationthat is required to support the use of operational systems. In somesituations, all the connectivity may come from a system that can'treasonably be called a GIS or CAD system. In others, separate systemsare likely to be the source of smaller components of the networkdefinition (e.g., control and measurement definitions, physical assetinformation, and common or specialized identifiers).

Data exchange through the Model Management system may be carried outaccording to the Common Information Model (CIM) specified as part of theIEC 61970 series of standards. The CIM recommends the use of theGeographic Markup Language (GML) for geographic and schematic forms ofpresentation for networks. Multiple forms of presentation can be handledby the combination of CIM and GML. Both CIM and GML call for XML-basedencoding.

CIM/GML-based interfaces, such as interfaces 240, 242, 244, 248, 250,252, 254, correspond to points at which the Model Management Gateway isabstracted from the systems with which it interacts. Such systems can beconfigured to provide or accept CIM/GML-based constructs. ModelManagement Development should include close coordination with futuredevelopment of CIM/GML-based interfaces to back-office and operationalsystems. Most of the interfaces 240, 242, 244, 248, 250, 252, 254 areconfigured for two-way communications as illustrated by the associatedexemplary directional arrows 212, 214, 216, 218, to support the flow ofdata in and out.

Model Management Gateway 260 includes Network Synchronization Manager262 and the Electrical Network Model 264, which stores the informationexchanged via the CIM and GML. The Model Management Gateway 260 performsa number of functions, including: acting as a staging and aggregationarea for data until corrected and approved for use in OperationalSystems; exchanging data based on CIM and OGIS (GML) standards;supporting different data input systems (GIS, CAD, RDBMS); supportingmultiple target operational systems; and extending existing products,for example, Enterprise Gateway.

Model Management Gateway 260 responsibilities include:

-   -   synchronization of different network representations used in        operational and “back-office” systems;    -   acceptance of information defining the structure of the network        from many and varying sources;    -   maintenance of a record of the structure of the electric        network;    -   aggregation of network information into a combined form that        fulfills the needs of operational systems;    -   validation of the integrity of network information (e.g.        phasing, voltage levels, etc.);    -   correction and augmentation of network information;    -   management of multiple static forms of presentation for        electrical networks (including geographic and schematic forms);    -   making initial network information available to operational        systems;    -   accepting updates and corrections from operational systems;    -   feeding corrections and other updates back to “source” systems;    -   accepting packaged updates from “source” systems;    -   making packaged updates available to operational systems;    -   versioning of network information; and    -   control over the processes associated with synchronizing network        representations.

Because there are several possible systems that may provide data, theModel Management Gateway 260 may be configured as the staging ground forthat data. The stored form of the model may be readily convertible toCIM and GML encodings, while at the same time providing the means toprovide the services required of the Model Management framework.

In an exemplary configuration, Oracle may be used as a repository forthe Enterprise Gateway. Further, in an exemplary configuration, OracleLocator technology may be used for storing the geometric parts of themodel including both geographic and schematic models.

Network Synchronization Manager 262 is the master manager of theoperation because it will determine or be told from outside sourceswhich data has to be processed and which processes are to be invoked toprocess the data. In this regard, it is important that NetworkSynchronization Manager 262 be configured to take data from othersystems as input for the process flow of the data.

Network Synchronization Manager 262 responsibilities include:

-   -   data import;    -   data aggregation (adding data from other sources);    -   data validation/inspection;    -   data cleanup;    -   data acceptance; and    -   data export.

Operational Systems including EMS 222, DMS 224, OMS 226, and MDM 228have multiple responsibilities. Within the context of Model Management,they need to be configured to:

-   -   Accept initial network definitions and graphical presentations        in CIM/GML form;    -   Accept incremental updates to network definitions and graphical        presentations in CIM/GML form;    -   Maintain operational network representation;    -   Provide support for “off-line” representations (e.g. case        studies, simulation);    -   Provide final control over introduction of updates; and    -   Notify Model Management Gateway 260 of introduced updates.

The present subject matter provides a reasonable and proven method ofversion controlling normal state network models in industry fields thatcan be easily extended and customized based on different businessrequirement. With this methodology, the system is able to handle/versioncontrol large-scale CIM data efficiently and effectively, and providemodel validation. It is especially useful where the data changesfrequently and needs to be validated with strict rules. Moreover, itprovides a fundamental data structure (full model), which is thesnapshot for the current whole model. Based on this, utilities caneasily develop a variety of applications for their business.

This written description uses examples to disclose the invention,including the best mode, and also to enable any person skilled in theart to practice the invention, including making and using any devices orsystems and performing any incorporated methods. The patentable scope ofthe invention is defined by the claims, and may include other examplesthat occur to those skilled in the art. Such other examples are intendedto be within the scope of the claims if they include structural elementsthat do not differ from the literal language of the claims, or if theyinclude equivalent structural elements with insubstantial differencesfrom the literal language of the claims.

What is claimed is:
 1. A method for providing version control for amodel, comprising: providing a database; dividing the database intoplural logical areas including at least a working model logical area anda permanent model logical area; importing data into the working modellogical area by temporarily storing imported data in the working modellogical area, wherein the imported data corresponds to incrementalchange data associated with a network of an electric utility; validatingthe incremental change data to provide validated incremental changedata, wherein the validation is at least partially based on connectivitybetween assets of the electric utility in the network, wherein thevalidation of the incremental change data includes validating anintegrity of the incremental change data between the assets connected toeach other; associating version information that is based at least inpart on a timestamp with the validated incremental change data, whereinthe timestamp is associated with a time of the importing of the importeddata; and permanently storing the validated incremental change data andassociated version information in the permanent model logical area. 2.The method of claim 1, further comprising: providing a full modellogical area in the database; importing full model data into the fullmodel logical area; further validating the incremental change data basedat least in part on the full model data; merging the validatedincremental change data with data stored in the working model logicalarea; and storing the merged data in the full model logical area.
 3. Themethod of claim 2, wherein validation is based at least in part on aprofile of a standard model.
 4. A method for controlling operation of anetwork, comprising: providing a database; dividing the database intoplural logical areas including at least a working model logical area anda permanent model logical area, wherein the imported data corresponds toincremental change data associated with a network of an electricutility; importing data into the working model logical area bytemporarily storing imported data in the working model logical area;validating the incremental change data to provide validated incrementalchange data, wherein the validation is at least partially based onconnectivity between assets of the electric utility in the network,wherein the validation of the incremental change data includesvalidating an integrity of the incremental change data between theassets connected to each other; associating version information that isbased at least in part on a timestamp with the validated incrementalchange data, wherein the timestamp is associated with a time of theimporting of the imported data; permanently storing the validatedincremental change data and associated version information as versioncontrolled data in the permanent model logical area; and exporting theversion control data for use by network applications.
 5. An apparatusfor controlling operation of a network, comprising: a database dividedinto plural logical areas including at least a working model logicalarea and a permanent model logical area by temporarily storing importeddata in the working model logical area, wherein the imported datacorresponds to incremental change data associated with a network of anelectric utility; a data import manager for receiving data into theworking model logical area; a validation manager configured to validatethe incremental change data to provide validated incremental changedata, wherein the validation is at least partially based on connectivitybetween assets of the electric utility in the network, wherein thevalidation of the incremental change data includes validating anintegrity of the incremental change data between the assets connected toeach other; a version control configured to associate versioninformation based at least in part on a timestamp with the data receivedby said data import manager, wherein the timestamp is associated with atime of the importing of the imported data; and an archive managerconfigured to permanently store the validated incremental change dataand associated version information as version controlled data in thepermanent model logical area of the database.
 6. The apparatus as inclaim 5, further comprising: a full model logical area in said database;wherein the validation manager is configured to further validate theincremental change data received by said import manager based at leastin part on data stored in said full model logical area; a baselinemanager configured to merge the validated incremental change data withdata stored in the working model logical area; and a database managerconfigured to store the merged data in the full model logical area.